-
Notifications
You must be signed in to change notification settings - Fork 128
Add sticky event support #3513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: voip-team/rebased-multiSFU
Are you sure you want to change the base?
Add sticky event support #3513
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is added a new lab option?
It is just for Netlify? so why a review?
} | ||
|
||
// There was call membership events at some point in the timeline. | ||
return timeline.getEvents().some( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no API to get the sticky events? Having the sticky key doesn't make the event sticky.
I am a bit lost with what this method is expecting to do
} | ||
|
||
// There was call membership events at some point in the timeline. | ||
return timeline.getEvents().some( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this method exactly? Try some heuristic to see if a room is a call room? like type": "org.matrix.msc3417.call"
?
Or if there might be an active call?
And now it is checking for possible past sticky events (but potentially not anymore sticky)?
I don't get what this doing and what for
Sorry failed to change the title 🤦 |
- use new js-sdk - use custom synapse - don't filter rooms by existing call state events Signed-off-by: Timo K <[email protected]>
Signed-off-by: Timo K <[email protected]>
eb586a5
to
6580555
Compare
… toger5/sticky-events-version
Signed-off-by: Timo K <[email protected]>
Signed-off-by: Timo K <[email protected]>
This uses the newly merged sticky event work. Largely this just adds a new setting to enable it when starting a call. Sticky events will always work if someone else on the call enables it.
Testing options
Netilify
homeserver
url parameter to link your custom homeserver (example:https://localhost:3000?homeserver=https%3A%2F%2Ftest.com
encoding is of course needed)Locally
pull/download this PR/branch
start the docker dev env via
yarn backend
(synapse, livekit sfu, nginx, jwt authorizationService...)(in a new terminal) start EC
yarn dev
Now it should "just work" to do calls on https://localhost:3000